inject macro definitions during compilation time#3165
Merged
eder-matheus merged 1 commit intoMay 15, 2025
Conversation
Signed-off-by: Eder Monteiro <emrmonteiro@precisioninno.com>
Member
Author
|
@oharboe FYI. |
maliberty
approved these changes
May 14, 2025
Member
|
Ugly but effective. I'd like to see if we can upstream a change to have an build option that avoids the need for such tricks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've found this strategy to set the TIME, DATE and TIMESTAMP as constants without breaking Yosys build, and also without breaking the check for the C++14 support (the error that was happening with verilator).
I've tested it and I can see that what the C++ compiler sees is the constant "0", so I believe it will restore the behavior of having constant date/time in the binary.